From 481fa232a9c660da96c1d3d1218349674e5acb79 Mon Sep 17 00:00:00 2001 From: oliskoli Date: Sat, 20 Sep 2008 20:01:10 +0000 Subject: [PATCH] Add support for Jelbert GeoTagger data files (.jtr). --- vecs.c | 2 +- xmldoc/formats/jtr.xml | 28 ++++++++++++++++++++++++++++ 2 files changed, 29 insertions(+), 1 deletion(-) create mode 100644 xmldoc/formats/jtr.xml diff --git a/vecs.c b/vecs.c index abfb2f3c8..a6f48b0f1 100644 --- a/vecs.c +++ b/vecs.c @@ -850,7 +850,7 @@ vecs_t vec_list[] = { #if CSVFMTS_ENABLED { &geotagger_vecs, - "geotagger", + "jtr", "Jelbert GeoTagger data file", "jtr" }, diff --git a/xmldoc/formats/jtr.xml b/xmldoc/formats/jtr.xml new file mode 100644 index 000000000..0d39be41e --- /dev/null +++ b/xmldoc/formats/jtr.xml @@ -0,0 +1,28 @@ + + From the file format description: + + + The JTR file format is used by the Jelbert GeoTagger device to record + location information relating to where photographs have been taken. + One record entry is created for each press of the shutter on the + camera. + + + The JTR file format will be updated in the future so it is important to + check for the current version ID within the file that is present at the + beginning of each line of data. It is currently “GEOTAG2” + + + Each line of the JTR file currently starts with the word “GEOTAG2” + followed by a comma and then two NMEA sentences separated by a + comma character with a CR at the end. The $GPRMC (date, time and + position) data is followed by the $HCHDG (magnetic compass) data. + + + Although the $GPRMC data segment contains a compass bearing, this + should be ignored unless the $HCHDG compass direction is null which + can happen if the electronic compass is switched off. Use the magnetic + compass bearing in preference to the GPS derived compass. + The two NMEA checksums can be ignored for the time being. + + -- 2.30.2